home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
ftp.cs.arizona.edu
/
ftp.cs.arizona.edu.tar
/
ftp.cs.arizona.edu
/
icon
/
newsgrp
/
group93b.txt
/
000111_icon-group-sender _Thu May 20 13:45:00 1993.msg
< prev
next >
Wrap
Internet Message Format
|
1993-06-16
|
1KB
Received: from owl.CS.Arizona.EDU by cheltenham.cs.arizona.edu; Sun, 23 May 1993 19:53:05 MST
Received: by owl.cs.arizona.edu; Sun, 23 May 1993 19:53:03 MST
Date: 20 May 93 13:45:00 GMT
From: mercury.hsi.com!mlfarm!rosie!ron@uunet.uu.net (Ronald Florence)
Organization: Maple Lawn Farm, Stonington, CT
Subject: Icon on a mixed-architecture network
Message-Id: <1993May20.134500.4321@mlfarm.com>
Sender: icon-group-request@cs.arizona.edu
To: icon-group@cs.arizona.edu
Status: R
Errors-To: icon-group-errors@cs.arizona.edu
I'm wondering what is the best way to install Icon on a network with
both Sun4 and Sun3 machines.
We build Icon programs here with the space-saving Unix header
#! /usr/local/bin/iconx
at the top of the executable files. This makes for speedy and compact
executables, but ignores the ICONX environment variable. Assuming
machines on the network have the appropriate Sun3 or Sun4 iconx on
their PATH, will the same executable run on either system? I don't
think there are any byte-swapping nasties between Sun3 and Sun4
architectures.
Second, are the prog.u1 and prog.u2 modules portable between these two
architectures? In other words, could I use the same IPATH to a common
library for both systems?
Any other suggestions about setting up Icon on a mixed architecture
network? Thanks.
--
Ronald Florence
ron@mlfarm.com